Skip to content

Settings and activity

9 results found

  1. 100 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Isaque commented  · 

    I fully agree @Emasoft

    "XAML is an UI markup language. Recently XAML addes native support for SVG elements. It means that you can export an entire prototype made in AdobeXD in XAML, and import it as the UI layer directly in Visual Studio or Visual Studio Mac. That would make UI prototyping and UI development amazingly fast."

    An error occurred while saving the comment
    Isaque commented  · 

    Another interesting possibility would be Adobe XD, to have a toolbox of customizable UI controls, with the following controls.

    https://github.com/Microsoft/xaml-standard/issues/146

    An error occurred while saving the comment
    Isaque commented  · 

    Here are two ideas:
    1: Make the code behind Adobe XD be XAML, ie the file generated by Adobe XD be a XAML file, and Adobe support the definition of the XAML standard.
    https://github.com/Microsoft/xaml-standard/issues/182
    2: Since the code behind of Adobe XD is XAML, implement an exporter of UI elements to XAML, how this would work:

    For example:
    Let's imagine that you drew a rectangle with yellow rounded corners and added the following text in it "Login", right after you've grouped it, and now you want this to be a button, simply you click convert to button, and then click on toggle For XAML or click show XAML code and copy to clipboard, then you just paste the code in Xamarin.Forms in Visual Studio.
    This would make life easier for millions of developers.

    Isaque shared this idea  · 
  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Isaque shared this idea  · 
  3. 151 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Isaque supported this idea  · 
  4. 222 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Kenneth, would you mind breaking out SWF import as a separate feature request? That way people can gauge whether people want both or which one is higher priority. I’ll remove SWF from the title here so it’s focused specifically on HTML import.

    Isaque supported this idea  · 
  5. 39 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Isaque supported this idea  · 
  6. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Isaque supported this idea  · 
  7. 239 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Isaque supported this idea  · 
  8. 95 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Can you tell us more about how you’d like this to work? Do you want XD to export image assets and insert them directly into the correct folders/filenames in an existing Xcode project? Or do you want XD to generate Objective-C / Swift code to create a brand new Xcode project?

    Isaque supported this idea  · 
  9. 270 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Isaque supported this idea  · 
    An error occurred while saving the comment
    Isaque commented  · 

    Export to Android Studio/Xcode
    Export/Convert button design, listview and screen transitions for Android/IOS XML formats

    both Android/iOS/Windows/Web, uses XML-based files to define the Graphical User Interface it means that the to build a Parse and an API to allow the design to be done only once and reused in the aforementioned platforms

    So a button looks like this in XIB (IOS/OSX UI file)

    `<!-- Button 1 -->
    <object class="IBUIButton" id="580622739">
    <reference key="NSNextResponder" ref="191373211"/>
    <int key="NSvFlags">292</int>
    <string key="NSFrame">{{20, 124}, {280, 37}}</string>
    <reference key="NSSuperview" ref="191373211"/>
    <reference key="NSWindow"/>
    <reference key="NSNextKeyView" ref="810145050"/>
    <bool key="IBUIOpaque">NO</bool>
    <string key="targetRuntimeIdentifier">IBCocoaTouchFramework</string>
    <int key="IBUIContentHorizontalAlignment">0</int>
    <int key="IBUIContentVerticalAlignment">0</int>
    <reference key="IBUIFont" ref="881065587"/> <!-- Button Font Type -->
    <int key="IBUIButtonType">1</int>
    <string key="IBUINormalTitle">Facebook</string> <!-- Button Name -->
    <reference key="IBUIHighlightedTitleColor" ref="587412318"/>
    <reference key="IBUINormalTitleColor" ref="523599070"/> <!-- Button Font Color -->
    <reference key="IBUINormalTitleShadowColor" ref="457053782"/>
    <reference key="IBUINormalBackgroundImage" ref="650551563"/> <!-- Button Background -->
    </object>
    So a button looks like this in XML (Android UI file)

    <Button
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:text="@string/button_text"
    android:drawableLeft="@drawable/button_icon"
    ... />

    So a button looks like this in XAML (Windows UI file)

    <Button>
    <Button.FontWeight>Bold</Button.FontWeight>
    <Button.Content>
    <WrapPanel>
    <TextBlock Foreground="Blue">Multi</TextBlock>
    <TextBlock Foreground="Red">Color</TextBlock>
    <TextBlock>Button</TextBlock>
    </WrapPanel>
    </Button.Content>
    </Button>

    So a button looks like this in HTML (WEB UI file)

    <button style="background:red; cursor:pointer">click me</button>