Hi everyone,
I'm forwarding you the mail below by Fabio, who currently has issue with
his mail account.
Here's my +1
Cheers
Stéphane
----------
Dear all,
as on the schedule I'd like to publicly release XEclipse 1.1 today (or
tomorrow).
These are the release notes:
Bug
[XECLIPSE-70] - Invalid text in delete dialog box
[XECLIPSE-84] - Invalid version displayed when editing a page
[XECLIPSE-87] - Cannot reconnect after disconnecting
[XECLIPSE-89] - Login name with space
Improvement
[XECLIPSE-23] - Double-clicking on a tree node should open the node
[XECLIPSE-73] - Add edit working set feature
[XECLIPSE-77] - In preview panel, display the current URL and allow
typing any URL
[XECLIPSE-78] - In preview pane, add right click action to open the
current URL in external browser
[XECLIPSE-81] - Let user decide if they want to overwrite the server
version rather than merge it
I've partially initiated the release process otherwise I will not
able, in case, to complete it at home (slow internet connection not
suitable for transferring several MB of stuff)
Let me know WDYT.
Cheers,
Fabio
----------
Hi,
I have noticed that we have javascript files lying at several places in the
xwiki web application.
Further we seem to be using lot of javascript code developed by many
independent OEM vendors.
All this makes very hard to understand what all components are present in
each js file.
I would like to know why we use such fragmented set of js code, where as
almost all the functionality could have been achieved by using single ajax
toolkit and any additional work could have been done by using plugins on top
of these tool kits. Every good ajax toolkits provides ways to extend and
there is a good library of useful plugins found for each.
In the xwiki application I have found at least 4 ajax toolkits:
general toolkits found
----------------------
scriptaculous
rico
prototype
yui
Further there are lot of other js code also lying around. Again I am not
sure if most of this is extension of one of the above toolkit or again these
are independent set of javascript code (ajax/dhtml widgets).
other js files found:
---------------------
wysiwyg editor
---------------
tiny_mce
wiki_editor
color picker
---------------
chwScripts
panels wizard
----------------
panelWizard
miscelaneous
---------------
ajaxSuggest
lightbox
tablefilterNsort
usersandgroups
tdwScripts
wzToolTip
Almost of the functionality present in these javascript file could have been
built using just one ajax toolkit.
Is there any attempt to clean this stuff.
To start with I suggest to keep all the possible js code a one place,
probably in scrips directory.
Next we can replace code by using agreed toolkit. This way lot of extra js
code would be removed and we would have much compact UI.
Also can someone mention 1 liners as what is the purpose of each js file we
use in xwiki.
I am planning to redesign the complete UI using ext-js and jquery and it
would help me a lot in knowing how can each be replaced with new component.
Like after a lot of hit and trial I found that if I include ext-js and rico
together, ext-js does not get loaded. So now I can replace whats being done
by rico toolkit with ext-js/jquery equivalent.
Let me know what are your opinions on this.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/very-fragmented-javscript-code-tp15561552p15561552.ht…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi devs,
the current templates for xwiki pages include a xhtml standard <DOCTYPE>
for any html page generated which triggers the standard mode CSS
interpretation in browsers (see
http://www.quirksmode.org/css/quirksmode.html for details). This causes
issues in applications that use GWT generated code (like XWatch) since GWT
does not work properly in standards mode yet (see
http://code.google.com/p/google-web-toolkit/issues/detail?id=1305 for
details). I propose to parametrize the document type definition (its
existance and type), thus allowing the developer to take control of the
type of document it generates, for each generated page.
The solutions would be:
- using a request parameter to specify the doctype
- using a $response function, just like $response.setContentType() to set
the doctype at render time (this solution might require post processing to
change the default generated doctype in the page).
WDYT?
Hi,
I'd like to start the release of the following modules in order to
release XE 1.3M2:
Is there any other module that also needs to be released?
XWiki Configuration Resources Tools 1.9
================================
** New Feature
* [XTCONFRES-8] - Add new LDAP authentication service parameters
Core/Web 1.3M2:
==============
** Bug
* [XWIKI-299] - Changing property layout of a list property in a
class doesn' work (multiple select yes/no)
* [XWIKI-1457] - Any user can write and execute groovy code
* [XWIKI-1621] - Changing parameters of list properties fails
* [XWIKI-1642] - Stylesheets are loaded twice
* [XWIKI-1651] - Different format for $doc.creationDate when $doc
is retrieved from cache
* [XWIKI-1661] - Endless 100% CPU task when saving page
containing ugly code
* [XWIKI-1949] - Deleting the most recent version from the
history does not update the actual document
* [XWIKI-1974] - Display pretty names in the propertyclass drop
down list
* [XWIKI-2030] - In the user tab on the administration page the
dialog box when deleting a user should be modified
* [XWIKI-2039] - Creating a group with the name of an existing
page should generate an error
* [XWIKI-2040] - api.User#isUserInGroup should not throw exceptions
* [XWIKI-2051] - Can't get properties values from a document's
api Object from another wiki
* [XWIKI-2052] - XWikiDocument.equals always returns false if a
document is compared to itself
* [XWIKI-2056] - The URL Factory should use the contextPath
instead of the contextName
* [XWIKI-2064] - DBListClass and DBTreeListClass are building
invalid SQL statements
* [XWIKI-2065] - XWikiHibernateStore.deleteWiki don't works
* [XWIKI-2066] - Migrator fails to upgrade sub wiki databases
* [XWIKI-2068] - Rights Manager does not clean deleted user/group
in all wikis
* [XWIKI-2074] - Database Migration fails when migrating from 1.0
or older directly to 1.2 without going through a 1.1 upgrade
* [XWIKI-2076] - "Content is not allowed in prolog" error while
migrating a database to 1.2
* [XWIKI-2078] - Missing translation entry for the title of the
Group Admin page
* [XWIKI-2079] - Fails to save document after migrating from a
1.0 or before database to 1.2
* [XWIKI-2080] - Server hangs while rendering certain pages
* [XWIKI-2086] - Only the 15 first groups are listed in the new
right management UI - there is no "Next" button or scrollbar to see
others
* [XWIKI-2087] - Attached files that we can't delete or link in
the Wiki pages
* [XWIKI-2090] - Attaching images with a name containing special
characters (é & è à ...) generates bugs (image are not displayed)
* [XWIKI-2097] - SkinAction tries the same path more than once
* [XWIKI-2101] - XWiki.clearName strips dots when using ascii
option even if stripDots option is set to false
* [XWIKI-2102] - Attachments should not contain non-alphanumeric
characters in the file name
* [XWIKI-2109] - Can't search page titles with the Lucene plugin
* [XWIKI-2119] - Authentication fails with current tomcat versions
* [XWIKI-2120] - DBList and DBTreeList queries should be just
parsed, not rendered
* [XWIKI-2122] - Too many empty lines when using IE in the Rights
Management UI
* [XWIKI-2126] - In IE6, there's no space in the document footer
between "last modified by Administrator" and "on "
* [XWIKI-2127] - Edit action buttons are split on two lines in IE6
** Improvement
* [XWIKI-1079] - LDAP Authentication
* [XWIKI-1834] - XWikiDocument.toString() should return the
document's full name
* [XWIKI-2055] - Move utility APIs from the api.XWiki class to a
new api.Util class
* [XWIKI-2057] - Deprecate XWiki.sendMessage() since there's now
a sendmail plugin for that
* [XWIKI-2083] - Improve the way DBList and DBTreeList generate
queries
* [XWIKI-2093] - Improper names for the URL components in
XWikiServletURLFactory
* [XWIKI-2095] - Display the parsed velocity template name in the
logs
* [XWIKI-2099] - SkinAction should use the first XWikiSkins
object found in the document, not just the one with number 0
* [XWIKI-2108] - XMLRPC servlet does not store all the page
metadata
* [XWIKI-2118] - Add class to UL in toc
** New Feature
* [XWIKI-1752] - Generic "error", "warning" and "notice" templates
* [XWIKI-2088] - Add a method to retrieve the e-mail address of a
user
* [XWIKI-2096] - Allow skin document attachments to override/
provide templates
** Task
* [XWIKI-1207] - Strikethrough XWiki syntax
* [XWIKI-1243] - Underline XWiki syntax
* [XWIKI-1245] - Italics XWiki syntax
* [XWIKI-1248] - Strong XWiki syntax
* [XWIKI-1665] - Build and deploy Maven site on our CI server
* [XWIKI-1866] - Document the Watchlist features
* [XWIKI-2049] - Lock down Maven plugin versions for build
reproducibility
* [XWIKI-2050] - Add a bridge to allow current XWiki code to use
XWiki components
* [XWIKI-2054] - Add Utility API to remove all non alpha numeric
characters from some text
* [XWIKI-2059] - Move deprecated methods in XWiki class into a
backward-compatibility Aspect
* [XWIKI-2067] - Validate that XWiki Core works on newly released
PostreSQL 8.3
* [XWIKI-2077] - Add Toucan skin to the default standard platform
WAR
* [XWIKI-2081] - Move cryptpassword tool to the sandbox for now
* [XWIKI-2082] - Move all tools build modules to the
com.xpn.xwiki.platform.tools groupId
* [XWIKI-2094] - Remove XWikiInterface interface which isn't used
* [XWIKI-2115] - Remove "disambiguation" template+resources
Panels 1.3
=========
** Bug
* [XAPANELS-42] - Some panels break the panel wizard
** Improvement
* [XAPANELS-39] - Modify the Syntax help panel so that it always
open a new page that lists all syntax options
** Task
* [XAPANELS-40] - Add new "Edit Modes" Editor Panel for the new
Toucan skin
Albatross 1.2
==========
** Bug
* [XSALBATROSS-10] - Accidentally reintroduced XWIKI-1749
* [XSALBATROSS-11] - Replacing style.css in the Administration
doesn't work
** Task
* [XSALBATROSS-12] - Deprecate old dodo alternate stylesheets
Toucan 1.0
=========
** Task
* [XSTOUCAN-1] - Create Toucan skin from xwiki.org
XE 1.3M2
========
** Bug
* [XE-193] - Wrong headings in Sandbox.WebHome
** Improvement
* [XE-190] - Add an empty line after the title in the Lucene
Search page
* [XE-195] - Make Toucan the new default skin in XWiki Enterprise
Hi,
I've been using Maven 2.1 snapshot built from maven trunk for more
than a week now and didn't get any issue.
I'd like to propose that we remove our old maven zip and replace it
with a recent trunk version.
This will allow:
* fixing lots of maven bugs we have since we're using an old maven
version
* putting us on the maven 2.1 release track. This will allow us to
detect any issue and report it to the maven team so that the final 2.1
release will work for us
Here's my +1
Thanks
-Vincent
Hi,
I've updated our official Maven install zip for building XWiki to a
newer version.
It's available on http://dev.xwiki.org/xwiki/bin/view/Community/Building
It would be good if you could update and start using this new version.
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Eclipse 1.1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWikiEclipse
XEclipse 1.1 introduces several bug fixes and improvements for a nicer
user experience.
Changes from 1.0.1:
* XECLIPSE-70 - Invalid text in delete dialog box
* XECLIPSE-84 - Invalid version displayed when editing a page
* XECLIPSE-87 - Cannot reconnect after disconnecting
* XECLIPSE-89 - Login name with space
* XECLIPSE-23 - Double-clicking on a tree node should open the node
* XECLIPSE-73 - Add edit working set feature
* XECLIPSE-77 - In preview panel, display the current URL and allow
typing any URL
* XECLIPSE-78 - In preview pane, add right click action to open the
current URL in external browser
* XECLIPSE-81 - Let user decide if they want to overwrite the server
version rather than merge it
For more information see the Release notes and instructions at:
http://code.xwiki.org/xwiki/bin/view/Extensions/XEclipseExtension
Thanks
-The XWiki dev team
Hi,
I'm proposing to make toucan the default skin in 1.3M2. Several reasons:
1) It's nicer and cleaner than Albatross
2) If we want to get feedback on it we need it to make it the default.
It's important to do this now so that we can deliver a perfect Toucan
for 1.3 final
3) One of the highlight of the 1.3 release is the new skin
Here's a big +1 from me.
Thanks
-Vincent
Hi devs,
I've just installed Archiva on http://laam.xpertnet.biz:8080/archiva/index.action
under my account there. Raffaello will probably move it somewhere
else in the near future.
http://laam.xpertnet.biz:8080/archiva
Right now I've configured it to:
* Remove snapshots that are older than 30 days
* Keep the last 2 snapshots artifacts
* Delete snapshots when a released version exist
Now let's monitor how it goes...
Thanks
-Vincent
Hi,
As planned I'd like to release 1.3M2. It was planned for today but
since we're still busy I propose to do the release over the week end
and on monday morning.
Is there anything we're still working on that prevents 1.3M2 from
being released? And if so when can you have these finished?
Thanks
-Vincent