Announcement

Collapse
No announcement yet.
X
Collapse
  • Page of 1
  • Filter
  • Time
Clear All
new posts
Previous template Next
    #1

    Reify issue: Balsamiq standalone readonly

    I'm experimenting with Reify for the first time and have come across several issues I'm not sure how to resolve:

    SGWT: 2013-03-22 Power
    Dev env: Eclipse Juno, GWT 2.5.1
    Browser: FF 19

    1) The demo video was very impressive and documentation gives hints on filling layouts (under "Space Filling & Fluid Layout"). Although my first attempt was to have a TabSet fill the screen. I placed a Vertical Tab into Balsamiq and put a grid inside it. While the grid appeared to have corrected filled the space of the tab, the TabSet itself was fixed size. What should I be doing to make this fill the browser window and resize with it?

    2) How should a RibbonBar/Group be represented in Balsamiq so that the tool imports properly? (Ideally, I'm trying to achieve the layout of having a set of RibbonBar/Group on top of the ListGrid in the TabSet)

    3) I'm using the standalone tool to watch the import change live as a I change the mockup in Balsamiq, but it seems after the tool refreshes the first time, Balsamiq is unable to write to the file. It appears as though the Eclipse Java process has a lock on the file. I would need to stop the GWT jetty server before Balsamiq is able to write to the file again.
    Tags: None
    #2
    1. The default is to fill space. You might have unchecked the "Fill Space" checkbox in the tool?

    2. What specific result are you looking for? Currently there is no default Balsamiq control that results in a SmartGWT RibbonBar, but the Reify docs discuss various ways of influencing what's generated.

    3. We haven't seem this, what platform are you on?

    Comment

      #3
      1. Just double checked, this is definitely ticked when I did the import. Attached is the test bmml file which contains nothing other than drag and dropped controls from Balsamiq. The end result looks like this.

      2. I'm just trying to re-create a UI that I have previously done already. It is similar to this screenshot, but has the TabSet tabs along the left with 32x32 icons.


      3. Just to note, I've found that even if I'm not automatically refreshing, just loading the bmml up in Reify causes the file to appear to be read-only to Balsamiq. I'm on Win 7 x64. Also just updated to SGWT Power 2013-03-29, Balsamiq 2.2.9, Adobe Air 11,6,602,180.
      Attached Files

      Comment

        #4
        Just reporting back that I don't have this issue under OS X 10.8.3

        First notable difference was the Win 7 x64 JRE was 1.7 and OS X was on 1.6.0_43.

        However after reverting Eclipse and the project runtime JRE to 1.6 I still have this problem on Win 7 x64.

        Comment

          #5
          1. We're reproducing this, we'll check on it

          2. Again, Balsamiq has no mockup elements that look like a RibbonBar, so nothing automatically translates to RibbonBar. But you can use the instructions in the BMML Importer docs to explicitly mark components so that they translate to specific classes.

          3. In Windows, do you get this with compiled mode? We suspect some kind of Eclipse interference here.

          Comment

            #6
            1. Any update on 1?

            2. Thanks, will investigate further.

            3. Apologies for not getting back on this issue sooner on this, but I can confirm that this is happening when using dev mode, and works fine when using compiled mode. Worth noting that in both cases I'm not visiting the page via debug URL (with gwt.codesvr in the URL)

            Comment

              #7
              1. This should be fixed, sorry for not following up.

              3. If it's Dev Mode only it's unlikely to be something we can fix. Note there's no particular reason to run Reify in Dev Mode; it's a tool with no GWT Java in it.

              However your explanation is a little strange. You're saying you're visiting the page with no gwt.codesvr in the URL. But doing so means you're running in compiled mode... ?

              Comment

                #8
                Originally posted by Isomorphic View Post
                However your explanation is a little strange. You're saying you're visiting the page with no gwt.codesvr in the URL. But doing so means you're running in compiled mode... ?
                Sorry that was a bit confusing. It's almost synonymous for me that Eclipse "Debug as" = GWT dev mode and Eclipse "Run as" = GWT compiled mode.

                Since as you know running dev mode is generally slower, I removed the gwt.codesrv part of the URL from my project's Reify bookmark. The issue went away when I used "Run as" instead of "Debug as".

                That raises another question: if Eclipse/GWT/Java requires "Run as" to play nicely with Reify reading the bmml file, doesn't it somewhat make the whole dev process less useful? (by needing "Run as" for Reify refresh to work makes us lose the ability to debug our application at the same time, unless Reify was intended to be deployed as a separate application altogether?)

                Comment

                  #9
                  It's unclear which piece of the system is causing this file locking issue for you. You've said various things that seem to indicate it's some combination of OS, JRE and GWT versions..

                  Yes you can run Reify as a totally standalone tool. It has no dependence on GWT or even on Eclipse. The simplest way to set up it as a separate process is just to download a *SmartClient* SDK and run start_embedded_server.bat and you'll have the tool at http://localhost:8080/tools/bmmlImporter.jsp.

                  If you have it set up this way, and you *still* have issues when reloading the page in Dev mode, then this will narrow down causes considerably.

                  Comment

                    #10
                    Originally posted by Isomorphic View Post
                    Yes you can run Reify as a totally standalone tool. It has no dependence on GWT or even on Eclipse. The simplest way to set up it as a separate process is just to download a *SmartClient* SDK and run start_embedded_server.bat and you'll have the tool at http://localhost:8080/tools/bmmlImporter.jsp.
                    This works well - no problem with the file locking, I'll go with this :)

                    However, the original "fill" problem with the bmml file I uploaded still exists. I'm using SmartClient_v83p_2013-05-16.

                    Comment

                      #11
                      That's a very strange result. It seems to imply that if a process running under GWT dev mode writes files to disk, GWT dev mode never releases them..

                      We'll have to wait to see if we receive any more similar reports.

                      As far as the fill issue, it was fixed for 4.0 only. We'll add the fix to 3.1 as well within a few days.

                      Comment

                      Previous template Next
                      Working...
                      X