On 2/2/06, Andreas Andreou <
[EMAIL PROTECTED]> wrote:
don't worry!
It's for 4.0
Michael Waluk wrote:
>Hi,
>
>I've lost track - but is this for Tapestry 4.0 or for a future 4.1?
>
>If for 4.1, will there be any further releases for 4.0 or was the alpha-7
>the last one?
>
>Thanks!
>- Michael
>
>
>On 1/31/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
>
>
>>I would go ahead and apply the fixes (hopefully the new regex performance
>>stays the same? ) , there are too many open bugs to even think about
>>releasing it yet. Once we get all of them closed (not all, but the big
>>ones...like comments, activating new pages, floating pane, etc..)
>>
>>On 1/31/06, Andreas Andreou <[EMAIL PROTECTED]> wrote:
>>
>>
>>>Any idea when beta-1 is coming?
>>>I'm currently holding up some bug fixes
>>>(http://tacoscomponents.jot.com/BugReporter/Bug29) till after that
>>>release.
>>>
>>>Jesse Kuhnert wrote:
>>>
>>>
>>>
>>>>I wouldn't beat yourself up over it too much. Doing anything in IE
>>>>
>>>>
>>>without a
>>>
>>>
>>>>decent debugger isn't something anyone should be subjected to ;) If you
>>>>
>>>>
>>>have
>>>
>>>
>>>>visual studio installed the script debugger should be installed by
>>>>
>>>>
>>>default,
>>>
>>>
>>>>otherwise the web script debugger thing is on any microsoft office cd.
>>>>
>>>>
>>>(it's
>>>
>>>
>>>>an optional install, you'll probably have to click on custom or
>>>>
>>>>
>>>whatever
>>>
>>>
>>>>equivalent phrasing they have).
>>>>
>>>>I totally lied about working on IE stuff last night anyways. Instead I
>>>>watched battlestar gallactica and played with tapestry ;) I'll really
>>>>
>>>>
>>>really
>>>
>>>
>>>>try and work on IE stuff tonight. I know something all encompassing is
>>>>broken anyways because the dialog widget isn't coming up properly in
>>>>responses. (in IE only of course...FF is way too easy to debug...I like
>>>>
>>>>
>>>the
>>>
>>>
>>>>FireBug extension.)
>>>>
>>>>On 1/31/06, Felix Sun <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>I am trying to fix the bug that FloatingPane can not be popuped in
>>>>>FloatingPaneExample page in MSIE browser .
>>>>>I have already on this for a couple of hours , almost a day, But It is
>>>>>
>>>>>
>>>too
>>>
>>>
>>>>>hard to find out where the error was thrown. It's really a pain in the
>>>>>
>>>>>
>>>ass
>>>
>>>
>>>>>of _javascript_ developer
>>>>>
>>>>>What kind of tools you guys use to find out the line number of a
>>>>>_javascript_ error thrown? or just see code by eyes? It's difficult to
>>>>>
>>>>>
>>>dig
>>>
>>>
>>>>>into dojo.
>>>>>I know there is no way to debug _javascript_. It really made me upset.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by: Splunk Inc. Do you grep through log
>>>files
>>>for problems? Stop! Download the new AJAX search engine that makes
>>>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>>>_______________________________________________
>>>Tacos-devel mailing list
>>>[email protected]
>>> https://lists.sourceforge.net/lists/listinfo/tacos-devel
>>>
>>>
>>>
>>
>>
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
