← Older revision

Revision as of 08:57, 11 June 2013

Line 55:

::Hi George, I created the Text Separator help screen. I see you beat me to the Alias one. I'm holding off on the Extension Module Edit(New) screen till I Skype later today with the PLT member/Bug Squad coordinator. The issue, the New Screen itself (2.5 or 3.0) is really like a Menu select type pop up screen. There isn't a 'Help' button, in fact only one button - 'Cancel.' The extension group Help screens were put together a bit different, Plugins even more so. Need to hash it out, but will probably go with something more generic, like [[Help30:Menus_Menu_Item_Manager_Edit]], which shows a Single Article Menu Item type. I actually need to go back and integrate in this [[Help30:Content_Article_Manager_Edit#Toolbar]] into the Menu Item Maganer Edit screen. It was my solution to Edit vs. New. In 2.5 or 3.0, creating a new or editing a Module(or anything) adjusts the Toolbar buttons accordingly.

−

::Good idea on the Options! The issue is they really are just a Modal pop up window in 2.5, no Help button to click in the pop up. In 3.0, they are now a dedicated options screens instead of the pop up which are available in certain component views, e.g. [[~~Help30~~:~~Content_Article_Manager_Options~~]]. Definite improvement over 2.5. Problem is, 3.0 is not constructing the Help screen URL for Options and pushing it back to a set landing page. Language Keys control the construction of the URL to the Help screen, JHELP_ name of help screen. Might have been because menu items can be added by extensions, the Help screen Language Keys are not in the master file, but created on the fly from the meta data of the specific menu item. I wasn't around for those discussions. The system menu items must be lacking that meta data, just a guess. The new Options screens in 3.0 will probably have to be done this way too, because add-on extensions can have options too.

+

::Good idea on the Options! The issue is they really are just a Modal pop up window in 2.5, no Help button to click in the pop up. In 3.0, they are now a dedicated options screens instead of the pop up which are available in certain component views, e.g. [[Help31:Components_Article_Manager_Options]]. Definite improvement over 2.5. Problem is, 3.0 is not constructing the Help screen URL for Options and pushing it back to a set landing page. Language Keys control the construction of the URL to the Help screen, JHELP_ name of help screen. Might have been because menu items can be added by extensions, the Help screen Language Keys are not in the master file, but created on the fly from the meta data of the specific menu item. I wasn't around for those discussions. The system menu items must be lacking that meta data, just a guess. The new Options screens in 3.0 will probably have to be done this way too, because add-on extensions can have options too.

::I think that's about the point I am on the 3.0's, 50% done, maybe a bit over. I found it was easier to cut and paste in the generic markup from similar items then change it. It is a painfully slow process and I know how hard it is. Yes, a lot of them never were even updated from 1.5. This is why I'm so thankful you have done so much with the 2.5 screens. It would be nice when 3.1 is released to say, 2.5 and 3.0 Help Screens are complete. My plan is too transclude as many Help Screens from 3.0 into 3.1 as possible, then same for 3.2, etc. Need to stop re-inventing the wheel every release.

@@ Line 15: / Line 15: @@
 * [[Need example
 * [[Need example 2
 ===User===
 When you create an account, you are given a personal user page. It would look something like this, <nowiki>User:DocsUser</nowiki> or User: followed by whatever username you used to register on the wiki. Think of it as your own personal page. A place to experiment with wiki code, new pages or pages you are thinking of creating.
@@ Line 23: / Line 25: @@
 Pages in this namespace are a like the title of the namespace states, a portal. Portal pages can take a user to many pages which are grouped together by a subject, such as [[Portal:Bug Squad]]. A page for all things relevant to being a Joomla! Bug Squad member.
 [[Category:Documentation Wiki Information]]

Joomla! Documentation - Changes related to "Client-side form validation" [en]

JDOC:Namespaces

User talk:Hutchy68

@@ Line 55: / Line 55: @@
 ::Hi George, I created the Text Separator help screen. I see you beat me to the Alias one. I'm holding off on the Extension Module Edit(New) screen till I Skype later today with the PLT member/Bug Squad coordinator. The issue, the New Screen itself (2.5 or 3.0) is really like a Menu select type pop up screen. There isn't a 'Help' button, in fact only one button - 'Cancel.' The extension group Help screens were put together a bit different, Plugins even more so. Need to hash it out, but will probably go with something more generic, like [[Help30:Menus_Menu_Item_Manager_Edit]], which shows a Single Article Menu Item type. I actually need to go back and integrate in this [[Help30:Content_Article_Manager_Edit#Toolbar]] into the Menu Item Maganer Edit screen. It was my solution to Edit vs. New. In 2.5 or 3.0, creating a new or editing a Module(or anything) adjusts the Toolbar buttons accordingly.
-::Good idea on the Options! The issue is they really are just a Modal pop up window in 2.5, no Help button to click in the pop up. In 3.0, they are now a dedicated options screens instead of the pop up which are available in certain component views, e.g. [[Help30:Content_Article_Manager_Options]]. Definite improvement over 2.5. Problem is, 3.0 is not constructing the Help screen URL for Options and pushing it back to a set landing page. Language Keys control the construction of the URL to the Help screen, JHELP_ name of help screen. Might have been because menu items can be added by extensions, the Help screen Language Keys are not in the master file, but created on the fly from the meta data of the specific menu item. I wasn't around for those discussions. The system menu items must be lacking that meta data, just a guess. The new Options screens in 3.0 will probably have to be done this way too, because add-on extensions can have options too.
+::Good idea on the Options! The issue is they really are just a Modal pop up window in 2.5, no Help button to click in the pop up. In 3.0, they are now a dedicated options screens instead of the pop up which are available in certain component views, e.g. [[Help31:Components_Article_Manager_Options]]. Definite improvement over 2.5. Problem is, 3.0 is not constructing the Help screen URL for Options and pushing it back to a set landing page. Language Keys control the construction of the URL to the Help screen, JHELP_ name of help screen. Might have been because menu items can be added by extensions, the Help screen Language Keys are not in the master file, but created on the fly from the meta data of the specific menu item. I wasn't around for those discussions. The system menu items must be lacking that meta data, just a guess. The new Options screens in 3.0 will probably have to be done this way too, because add-on extensions can have options too.
 ::I think that's about the point I am on the 3.0's, 50% done, maybe a bit over. I found it was easier to cut and paste in the generic markup from similar items then change it. It is a painfully slow process and I know how hard it is. Yes, a lot of them never were even updated from 1.5. This is why I'm so thankful you have done so much with the 2.5 screens. It would be nice when 3.1 is released to say, 2.5 and 3.0 Help Screens are complete. My plan is too transclude as many Help Screens from 3.0 into 3.1 as possible, then same for 3.2, etc. Need to stop re-inventing the wheel every release.