Historic:CssWork - Revision history

Admin: Admin moved page CssWork to Historic:CssWork

2024-12-04T05:19:48Z

Admin moved page CssWork to Historic:CssWork

← Older revision	Revision as of 05:19, 4 December 2024
(No difference)

Sir Finkus at 21:26, 20 September 2016

2016-09-20T21:26:13Z

← Older revision		Revision as of 21:26, 20 September 2016
Line 1:		Line 1:
			{{archival}}
	[[Development]] - parent		[[Development]] - parent

Michealpwalls: /* Use an IDE as an alternative */

2014-05-05T14:15:31Z

Use an IDE as an alternative

← Older revision		Revision as of 14:15, 5 May 2014
Line 169:		Line 169:
	The <sub>listsubs</sub> shell script is useful and very interesting, however if you are on a platform that cannot run Shell scripts or if you simply want a more integrated solution there are powerful tools that you can use.		The <sub>listsubs</sub> shell script is useful and very interesting, however if you are on a platform that cannot run Shell scripts or if you simply want a more integrated solution there are powerful tools that you can use.

	An IDE (''Integrated Development Environment'') makes working with large code bases much easy. ~~In my opinion~~, it is the ''only'' way to work with large and complex code bases.		An IDE (''Integrated Development Environment'') makes working with large code bases much easy. According to many developers, it is the ''only'' way to work with large and complex code bases.

	One of the many ways an IDE makes things so much easier is that they help you ''Navigate'' the project as well as integrating the different tools you need to use. In addition to navigating the Project, the IDEs automatically scan the code you have open to collect lists of very useful information for you including Procedures and Sub Procedures.		One of the many ways an IDE makes things so much easier is that they help you ''Navigate'' the project as well as integrating the different tools you need to use. In addition to navigating the Project, the IDEs automatically scan the code you have open to collect lists of very useful information for you including Procedures and Sub Procedures.

Michealpwalls: /* IDE as an Alternative */

2014-05-05T14:13:19Z

IDE as an Alternative

← Older revision		Revision as of 14:13, 5 May 2014
Line 166:		Line 166:


	=== IDE as an ~~Alternative~~ ===		=== Use an IDE as an alternative ===
	~~[[File:Windows-Eclipse-Navigator.png\|200px\|thumb\|right\|Eclipse on Windows, showing off the Code\|Project Navigators]]~~
	~~[[File:Windows-Geany-Sidebar.png\|200px\|thumb\|right\|Geany on Windows, showing off the SideBar]]~~

	The <sub>listsubs</sub> shell script is useful and very interesting, however if you are on a platform that cannot run Shell scripts or if you simply want a more integrated solution there are powerful tools that you can use.		The <sub>listsubs</sub> shell script is useful and very interesting, however if you are on a platform that cannot run Shell scripts or if you simply want a more integrated solution there are powerful tools that you can use.

Line 176:		Line 173:
	One of the many ways an IDE makes things so much easier is that they help you ''Navigate'' the project as well as integrating the different tools you need to use. In addition to navigating the Project, the IDEs automatically scan the code you have open to collect lists of very useful information for you including Procedures and Sub Procedures.		One of the many ways an IDE makes things so much easier is that they help you ''Navigate'' the project as well as integrating the different tools you need to use. In addition to navigating the Project, the IDEs automatically scan the code you have open to collect lists of very useful information for you including Procedures and Sub Procedures.

	Screen Shots from both Eclipse and Geany showing this capability ~~is attached for more information~~.		Here's a small gallery of Screen-Shots from both Eclipse and Geany showing off this capability:

			<gallery>
			File:Windows-Eclipse-Navigator.png\|Eclipse on Windows, showing off the Code\|Project Navigators
			File:Windows-Geany-Sidebar.png\|Geany on Windows, showing off the SideBar
			</gallery>

	If you think either Eclipse or Geany might be useful for you, ~~you can checkout~~ a simple guide ~~that has been started~~ on the Developer page:		If you think either Eclipse or Geany might be useful for you, a simple guide exists on the SoylentNews Wiki's Developer page:

	: [[Development#Integrated_Development_Environment\|Development - Integrated Development Environment]]		: [[Development#Integrated_Development_Environment\|Development - Integrated Development Environment]]

Michealpwalls: /* Got tired of scrolling through pages of perl code just to see what subs were in a module */

2014-05-05T14:04:52Z

Got tired of scrolling through pages of perl code just to see what subs were in a module

← Older revision		Revision as of 14:04, 5 May 2014
Line 165:		Line 165:
	Maybe someone else will find it useful as well.		Maybe someone else will find it useful as well.


			=== IDE as an Alternative ===
			[[File:Windows-Eclipse-Navigator.png\|200px\|thumb\|right\|Eclipse on Windows, showing off the Code\|Project Navigators]]
			[[File:Windows-Geany-Sidebar.png\|200px\|thumb\|right\|Geany on Windows, showing off the SideBar]]

			The <sub>listsubs</sub> shell script is useful and very interesting, however if you are on a platform that cannot run Shell scripts or if you simply want a more integrated solution there are powerful tools that you can use.

			An IDE (''Integrated Development Environment'') makes working with large code bases much easy. In my opinion, it is the ''only'' way to work with large and complex code bases.

			One of the many ways an IDE makes things so much easier is that they help you ''Navigate'' the project as well as integrating the different tools you need to use. In addition to navigating the Project, the IDEs automatically scan the code you have open to collect lists of very useful information for you including Procedures and Sub Procedures.

			Screen Shots from both Eclipse and Geany showing this capability is attached for more information.

			If you think either Eclipse or Geany might be useful for you, you can checkout a simple guide that has been started on the Developer page:

			: [[Development#Integrated_Development_Environment\|Development - Integrated Development Environment]]

	==Order css files are loaded when simple switch on user prefs page is selected viewing main page main page==		==Order css files are loaded when simple switch on user prefs page is selected viewing main page main page==

FunPika: /* Slash/DB/MySQL/MySQL.pm */ syntax highlight

2014-03-19T18:29:11Z

Slash/DB/MySQL/MySQL.pm: syntax highlight

Show changes

FunPika: /* User Menu */ syntax highlight

2014-03-19T18:26:31Z

User Menu: syntax highlight

← Older revision		Revision as of 18:26, 19 March 2014
Line 466:		Line 466:
	==User Menu==		==User Menu==

	<~~pre~~>		<syntaxhighlight lang="sql" line start="123">
	INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','Logout','logout','/my/logout',1,0,10);		INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','Logout','logout','/my/logout',1,0,10);
	~~124~~ INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','Preferences','preferences','/users.pl?op=edituser',1,0,20);		INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','Preferences','preferences','/users.pl?op=edituser',1,0,20);
	~~125~~ INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','Password','password','[% constants.real_rootdir %]/my/password',1,0,40);		INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','Password','password','[% constants.real_rootdir %]/my/password',1,0,40);
	~~126~~ INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','~[% user.nickname \| strip_literal %] ([% user.uid %])','me','/~[% user.nickname \| fixparam %]',1,0,50);		INSERT INTO menus (menu, label, sel_label, value, seclev, showanon, menuorder) VALUES ('users','~[% user.nickname \| strip_literal %] ([% user.uid %])','me','/~[% user.nickname \| fixparam %]',1,0,50);
	</~~pre~~>		</syntaxhighlight>
	<p> This code sets up the upper menu on http://slashcott.org/users.pl which is linked from your userid on the home page. The Preferences is wrong, as it needs to be all three links: Info, Homepage, Comments. This will allow users with low-bandwidth option set to easily get to the setting to unset low-bandwidth. -EP</p>		<p> This code sets up the upper menu on http://slashcott.org/users.pl which is linked from your userid on the home page. The Preferences is wrong, as it needs to be all three links: Info, Homepage, Comments. This will allow users with low-bandwidth option set to easily get to the setting to unset low-bandwidth. -EP</p>

FunPika: /* plugins/FireHose/mysql_dump.sql */ syntax highlighting

2014-03-19T18:12:24Z

plugins/FireHose/mysql_dump.sql: syntax highlighting

← Older revision		Revision as of 18:12, 19 March 2014
Line 426:		Line 426:

	==plugins/FireHose/mysql_dump.sql ==		==plugins/FireHose/mysql_dump.sql ==
	<~~pre~~>		<syntaxhighlight lang="sql">
	INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','firehose','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','firehose','no','',2,0, '');
	~~==>~~ INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','users','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','users','no','',2,0, '');
	INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','calendar.css','','','firehose','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','calendar.css','','','firehose','no','',2,0, '');
	~~==>~~ INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','users','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','users','no','',2,0, '');
	INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','comments.css','','','firehose','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','comments.css','','','firehose','no','',2,0, '');
	INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','index2','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','index2','no','',2,0, '');
	</~~pre~~>		</syntaxhighlight>

	<p>I believe that we are not using FireHose but it was needed to make the site work. As can be seen in the db dump above, it adds the firehose.css file to any of the user pages. Need to verify and then see if we can get the db purged of these values.</p>		<p>I believe that we are not using FireHose but it was needed to make the site work. As can be seen in the db dump above, it adds the firehose.css file to any of the user pages. Need to verify and then see if we can get the db purged of these values.</p>

FunPika: /* Slash/Apache/User/User.pm */ syntax highlighting

2014-03-19T18:11:15Z

Slash/Apache/User/User.pm: syntax highlighting

@@ Line 366: / Line 366: @@
 ==Slash/Apache/User/User.pm==
-<pre>
+<syntaxhighlight line start="548">
-{
 my %ops_my = (
-        inbox           => { args => 'op=list', uri => 'messages.pl' },
+         inbox           => { args => 'op=list', uri => 'messages.pl' },
-        # XXX change messages to be same as /inbox, move this to /my/preferences/messages
+         # XXX change messages to be same as /inbox, move this to /my/preferences/messages
-        messages        => { args => 'op=display_prefs', uri => 'messages.pl' },
+         messages        => { args => 'op=display_prefs', uri => 'messages.pl' },
-        comments        => { args => 'op=editcomm' },
+         comments        => { args => 'op=editcomm' },
-        homepage        => { args => 'op=edithome' },
+         homepage        => { args => 'op=edithome' },
-        password        => { args => 'op=changeprefs', uri => 'login.pl' },
+         password        => { args => 'op=changeprefs', uri => 'login.pl' },
-        logout          => { args => 'op=userclose', uri => 'login.pl' },
+         logout          => { args => 'op=userclose', uri => 'login.pl' },
-        misc            => { args => 'op=editmiscopts' },
+         misc            => { args => 'op=editmiscopts' },
-        amigos          => { args => 'op=friendview', uri => 'journal.pl' },
+         amigos          => { args => 'op=friendview', uri => 'journal.pl' },
-        bookmarks       => { args => 'op=showbookmarks' },
+         bookmarks       => { args => 'op=showbookmarks' },
-        firehose        => { args => 'op=userfirehose' },
+         firehose        => { args => 'op=userfirehose' },
-        preferences     => { args => 'op=displayprefs', uri => 'preferences.pl' },
+         preferences     => { args => 'op=displayprefs', uri => 'preferences.pl' },
-        tags            => { args => 'op=showtags' },
+         tags            => { args => 'op=showtags' },
-        journal         => { args => 'op=list', uri => 'journal.pl' },
+         journal         => { args => 'op=list', uri => 'journal.pl' },
-<h2>sql/mysql/defaults.sql</h2>
+        friends         => { args => 'op=friends', uri  => 'zoo.pl' },
-<pre>
+        default         => { args => 'op=edituser' }
-INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond, lowbandwidth) VALUES ('stylesheet','text/css','screen, projection','base.css','','','','no','',1,0, "","no");
+);
-INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond, lowbandwidth) VALUES ('stylesheet','text/css','screen, projection','comments.css','','','comments','no','',2,0, "","no");
+</syntaxhighlight>
 ==plugins/FireHose/mysql_dump.sql ==

FunPika: Some formatting and syntax highlighting.

2014-03-19T18:02:56Z

Some formatting and syntax highlighting.

← Older revision		Revision as of 18:02, 19 March 2014
Line 1:		Line 1:
	[[Development]] - parent		[[Development]] - parent

	~~<h2>~~AudioGuy~~</h2>~~		== AudioGuy ==

	* [[AudioGuyWorkNotes]] What I am actually working on will be found here.		* [[AudioGuyWorkNotes]] What I am actually working on will be found here.


	~~<h2>~~Note - paulj~~</h2>~~		== Note - paulj ==

	With javascript on, when I submit a story using the submit story link, and use the preview function, the background of the preview is solid red. Not just the header, the body as well.		With javascript on, when I submit a story using the submit story link, and use the preview function, the background of the preview is solid red. Not just the header, the body as well.


	~~<h2>~~Related pages ~~</h2>~~		== Related pages ==

	This is getting too big, and much of it has nothing to do directly with css, so I have moved this index to:		This is getting too big, and much of it has nothing to do directly with css, so I have moved this index to:
Line 17:		Line 17:


	~~<h2>~~Unanswered Questions~~</h2>~~		== Unanswered Questions ==
	* The templates are individually output by routine slashDisplay(), but how is the order of delivery determined, and how does one insure a new template goes to the right place on the page?		* The templates are individually output by routine slashDisplay(), but how is the order of delivery determined, and how does one insure a new template goes to the right place on the page?
	* The users home page link goes to /my/homepage. I can find no apache redirect for this nor is there a 'my' folder anywhere. I am guessing this is done in the apache perl module, through some redirects that hook into Apache innards. It is hard to be sure what script is actually being called first. I am assuming it is users. Once an edit is made, you are in /users.pl without /my/		* The users home page link goes to /my/homepage. I can find no apache redirect for this nor is there a 'my' folder anywhere. I am guessing this is done in the apache perl module, through some redirects that hook into Apache innards. It is hard to be sure what script is actually being called first. I am assuming it is users. Once an edit is made, you are in /users.pl without /my/
Line 141:		Line 141:


	~~<h2>~~Got tired of scrolling through pages of perl code just to see what subs were in a module~~</h2>~~		==Got tired of scrolling through pages of perl code just to see what subs were in a module==

	So wrote this, now in /usr/local/sbin/listsubs.sh:		So wrote this, now in /usr/local/sbin/listsubs.sh:
Line 166:		Line 166:


	~~<h2>~~Order css files are loaded when simple switch on user prefs page is selected viewing main page main page~~</h2>~~		==Order css files are loaded when simple switch on user prefs page is selected viewing main page main page==

	* base.css?T_2_5_0_272 The numbers are the slash verion number (from one of the docs).		* base.css?T_2_5_0_272 The numbers are the slash verion number (from one of the docs).
Line 174:		Line 174:
	* print.cssT_2_5__0_272		* print.cssT_2_5__0_272

	~~<h2>~~Follow a page link from the main page to an individual article page ~~</h2>~~		==Follow a page link from the main page to an individual article page ==

	* Link: http://soylentnews.org/article.pl?sid=14/02/18/0336229		* Link: http://soylentnews.org/article.pl?sid=14/02/18/0336229
	* article.pl is foind in slash/themes/slashcode/htdocs/article.pl So 'slashcode' is treated as a theme.		* article.pl is foind in slash/themes/slashcode/htdocs/article.pl So 'slashcode' is treated as a theme.

	~~<h2>~~article.pl~~</h2>~~		==article.pl==
	The stuff of interest to us		The stuff of interest to us

	<~~pre~~>		<syntaxhighlight>

	use Slash; -------- located in /local/lib64/perl5/slash.pm		use Slash; -------- located in /local/lib64/perl5/slash.pm
Line 281:		Line 281:
	(EOF)		(EOF)

	</~~pre~~>		</syntaxhighlight>


	~~<h2>~~Slash/DB/MySQL/MySQL.pm~~</h2>~~		==Slash/DB/MySQL/MySQL.pm==

	<pre>		<pre>
Line 364:		Line 364:


	~~<h2>~~Slash/Apache/User/User.pm~~</h2>~~		==Slash/Apache/User/User.pm==

	<pre>		<pre>
Line 426:		Line 426:


	~~<h2>~~plugins/FireHose/mysql_dump.sql ~~</h2>~~		==plugins/FireHose/mysql_dump.sql ==
	<pre>		<pre>
	INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','firehose','no','',2,0, '');		INSERT INTO css (rel, type, media, file, title, skin, page, admin, theme, ctid, ordernum, ie_cond) VALUES ('stylesheet','text/css','screen, projection','firehose.css','','','firehose','no','',2,0, '');
Line 444:		Line 444:
	<p>I think there was some firehose slashboxes that showed up in the users pages. They needed to be wider than the default, so they patched those pages with the firehose.css. Next step is to get a current dump of the two css tables. The important part is I know what files are for what parts of the code. Slashcode.css is the theme css file slashcode-lite.css is the style file that is called by a user pref. This means I need to fix comments.css to remove the theme elements I inserted and put them in the theme file. I still need to make sure that the changes that benefited the Simplified theme stay intact. -EP</p>		<p>I think there was some firehose slashboxes that showed up in the users pages. They needed to be wider than the default, so they patched those pages with the firehose.css. Next step is to get a current dump of the two css tables. The important part is I know what files are for what parts of the code. Slashcode.css is the theme css file slashcode-lite.css is the style file that is called by a user pref. This means I need to fix comments.css to remove the theme elements I inserted and put them in the theme file. I still need to make sure that the changes that benefited the Simplified theme stay intact. -EP</p>

	~~<h2>~~fonts~~</h2>~~		==fonts==

	<pre>		<pre>
Line 465:		Line 465:
	</pre>		</pre>

	~~<h2>~~User Menu~~</h2>~~		==User Menu==

	<pre>		<pre>
Line 475:		Line 475:
	<p> This code sets up the upper menu on http://slashcott.org/users.pl which is linked from your userid on the home page. The Preferences is wrong, as it needs to be all three links: Info, Homepage, Comments. This will allow users with low-bandwidth option set to easily get to the setting to unset low-bandwidth. -EP</p>		<p> This code sets up the upper menu on http://slashcott.org/users.pl which is linked from your userid on the home page. The Preferences is wrong, as it needs to be all three links: Info, Homepage, Comments. This will allow users with low-bandwidth option set to easily get to the setting to unset low-bandwidth. -EP</p>

	~~<h2>~~Refernces to css in the man pages in /usr/local/share/man/man3~~</h2>~~		==Refernces to css in the man pages in /usr/local/share/man/man3==
	<pre>		<pre>
	grep -i css *		grep -i css *
Line 507:		Line 507:


	~~<h2>~~CSS commit for Feb 23~~</h2>~~		==CSS commit for Feb 23==

	<p>		<p>