don't know what to think, our development times have drastically reduced
using the visual approach but
I agree that we cannot trust this framework anymore, at least in this
situation.
I still hope will give us a good alternative SOON and that NB 7 will include
a nice visual web editor as well.
I also hope that the open source community will be strong enough to continue
developing this library, because it's really good
once again: please Sun, help people who believe and believed in your
innovative tools
matroska wrote:
>
> Yes we have that problem too. That kind of problem make my firm to avoid
> the usage of woodstock for the next big web application. This is very
> sad as I am a big fan of woodstock.
>
> Yours faithfully
> Tobia Loschiavo
>
> autozoom ha scritto:
>> I don't have the rights to comment on that issue, just asked for them.
>> I anticipate the problems here, maybe you can copy and paste everything
>> there:
>> (notice that I am using FF3 portable because it cannot exist together
>> with
>> FF2, but everything is the same with a standard FF3 installation)
>>
>> - from time to time I get this javascript error:
>> [Exception... "Component is not available" nsresult: "0x80040111
>> (NS_ERROR_NOT_AVAILABLE)" location: "JS frame ::
>> file:///D:/mauro/programmi/portable/platform/PortableApps/FirefoxPortable/App/firefox/components/nsSessionStore.js
>> :: sss_saveState :: line 1901" data: no]
>>
>> - the main issue is that (it seems randomly) my buttons and other
>> components
>> don't get dressed with the proper style from the CSS or from the style
>> attribute, so I get plain grey buttons even if the background image is
>> different (it doesn't happen in FF2, of course)
>>
>> - drop down component doesn't react to the width property in style
>> attribute, so it's always the width of the longest label
>>
>> in general the styling engine seems to have problems, and the issues
>> disappear from time to time if you hit reload
>>
>>
>> Pete Lebet wrote:
>>
>>> Hi autozoom
>>> Can you describe your Woodstock 4.2 Firefox 3 problems in issue
>>> 1299? Does it simply not load youtr app at all or are specific
>>> components broken?
>>>
>>> Thanks,
>>> Pete
>>>
>>> autozoom wrote:
>>>
>>>> I just downgraded my application from 4.3b5 to 4.2ga
>>>> I had to reinstall NB6.5, which comes with Woodstock 4.2GA (and not 4.2
>>>> build 3 as stated in the documentation). I'd like to have a
>>>> confirmation
>>>> from Sun guys on this.
>>>>
>>>> I wasn't able to downgraded a pre-existant NB 6.5 installation because
>>>> when
>>>> you uninstall Visual JSF plugin then you cannot install it again
>>>> without
>>>> getting an error.
>>>>
>>>> Then, on a fresh NB 6.5 installation (without importing previuos
>>>> settings) I
>>>> had to manually import the libraries and servers by copying the xml
>>>> files
>>>> around in my home directory.
>>>>
>>>> Then I had to modify some of my code, because the "onLoad" attribute of
>>>> head
>>>> tag doesn't exist in 4.2GA, so I implemented a workaround to achieve
>>>> the
>>>> same result.
>>>>
>>>> Now everything works as before.
>>>>
>>>> And now I am waiting impatiently for the Firefox 3 patch for Woodstock
>>>> 4.2
>>>>
>>>>
>>>> Stephan Bardubitzki-3 wrote:
>>>>
>>>>
>>>>> If you use NetBenas could you share your experience in downgrading
>>>>> Woodstock?
>>>>>
>>>>> autozoom wrote:
>>>>>
>>>>>
>>>>>> Ok I will update the issue when I am ready with the downgraded
>>>>>> application.
>>>>>> But Sun people seemed to have it very clear in mind that there are
>>>>>> issues
>>>>>> with FF3.
>>>>>>
>>>>>>
>>>>>> Pete Lebet wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi autozoom,
>>>>>>> It would be a great help if you could update issue 1299 with
>>>>>>> the
>>>>>>> FF3 problems you are seeing with 4.2.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> autozoom wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Last week there was a public call conference where Sun engineers
>>>>>>>> told
>>>>>>>> us
>>>>>>>> that
>>>>>>>> Woodstock is abandoned.
>>>>>>>> Last ufficial release is 4.2 and 4.3 builds will never be
>>>>>>>> supported.
>>>>>>>> Sun also said that they would at least fix (or help fixing) the
>>>>>>>> Firefox
>>>>>>>> 3
>>>>>>>> problem in version 4.2
>>>>>>>>
>>>>>>>> Now, when is this going to happen? I am downgrading my production
>>>>>>>> system
>>>>>>>> to
>>>>>>>> 4.2, and I need at least to know when I can start using FF3
>>>>>>>>
>>>>>>>> Sun, any word?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>>>>>>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>>>>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>>
>>>
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/Sun%2C-here-we-are-again-tp20682289p20819150.html
Sent from the Project Woodstock - Users mailing list archive at Nabble.com.